Skip to content

One package: the action installs @vosjs/cli alone - #2

Merged
hblee12294 merged 2 commits into
mainfrom
one-package
Sep 2, 2026
Merged

One package: the action installs @vosjs/cli alone#2
hblee12294 merged 2 commits into
mainfrom
one-package

Conversation

@hblee12294

Copy link
Copy Markdown
Member

The take pipeline and the vos.so verbs ship inside @vosjs/cli since 0.9.0 (one package, every verb); @vosso/vos-plugin is a forwarding shim now. The install step and the README's license line say so.

The take pipeline and the vos.so verbs ship inside @vosjs/cli since 0.9.0;
@vosso/vos-plugin is a forwarding shim.
…ushes from main only and commits it

Every keyed run moved the tracked vos one version ahead of test/vos.json,
so the next run, on any branch, was refused as a stale base. Now the
action copies the take's vos.json back to the tracking path after a push
(a workflow commits it), the dogfood hands the key to push events only so
two branches never race for one base, and main commits the moved base
right after. The tracked base moves to the version the last keyed run
created.
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Release media for ci-7

Not pushed: no VOS_API_KEY was given, so the take stayed in the runner. Add the secret and the next run versions it on your shelf.

Channel Asset Size Bytes Length Moment
cws screenshot 1280x800 391 KB 0.8 s
cws screenshot 1280x800 374 KB 4.2 s
cws small-promo-tile 440x280 98 KB 0.8 s
cws marquee 1400x560 495 KB 0.8 s
og card 1200x630 472 KB 0.8 s

Skipped, with the reason:

  • cws icon: an icon is brand art, not footage — supply it from the kit

Verifier: 0 problems across 5 assets, re-measured from their bytes.

The kit is attached to the run as the artifact release-kit-ci-7. Made by vos: the next release is a re-render of the same actions.json, not a re-shoot.

@hblee12294
hblee12294 merged commit d852552 into main Sep 2, 2026
1 check passed
@hblee12294
hblee12294 deleted the one-package branch September 2, 2026 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant